Skip to content

Add the call-log-classifier lambda - #8592

Closed
huydhn wants to merge 1 commit into
gh/huydhn/3/basefrom
gh/huydhn/3/head
Closed

Add the call-log-classifier lambda#8592
huydhn wants to merge 1 commit into
gh/huydhn/3/basefrom
gh/huydhn/3/head

Conversation

@huydhn

@huydhn huydhn commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Stack from ghstack (oldest at bottom):

Impact: none yet -- no S3 notification points at this function
Risk: low

What

A small lambda that triggers log classification when a job log lands in
s3://ossci-raw-job-status/log/. It maps the S3 key to a repo (log/<id> is
pytorch/pytorch, log/<owner>/<repo>/<id> names its own) and asynchronously
invokes log_classifier.

[ghstack-poisoned]
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
torchci Ignored Ignored Aug 20, 2026 7:36pm

Request Review

@huydhn

huydhn commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

Superseded: the classifier invoke is folded into gha-log-uploader (#8591). The tail this split was meant to avoid came from invoking the classifier synchronously, not from doing it in the same function -- InvocationType: "Event" fixes it without a second lambda, an S3 notification, or re-parsing the repo and job id back out of the S3 key.

@huydhn huydhn closed this Aug 20, 2026
@huydhn

huydhn commented Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

No need to review this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant